The ypbind service must not be running if no network services utilizing it are enabled.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-89635	VRAU-SL-000540	SV-100285r1_rule		Medium

Description
Disabling the "ypbind" service ensures the system is not acting as a client in a NIS or NIS+ domain when not required.

STIG	Date
VMware vRealize Automation 7.x SLES Security Technical Implementation Guide	2018-10-12

Details

Check Text ( C-89327r1_chk )
If network services are using the "ypbind" service, this is not applicable. To check that the "ypbind" service is disabled in system boot configuration, run the following command: # chkconfig "ypbind" --list Output should indicate the "ypbind" service has either not been installed, or has been disabled at all run levels, as shown in the example below: ypbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off Run the following command to verify "ypbind" is disabled through current runtime configuration: # service ypbind status If the service is disabled the command will return the following output: Checking for service ypbind unused If the service is running, this is a finding.

Check Text ( C-89327r1_chk )

If network services are using the "ypbind" service, this is not applicable.

To check that the "ypbind" service is disabled in system boot configuration, run the following command:

# chkconfig "ypbind" --list

Output should indicate the "ypbind" service has either not been installed, or has been disabled at all run levels, as shown in the example below:

ypbind 0:off 1:off 2:off 3:off 4:off 5:off 6:off

Run the following command to verify "ypbind" is disabled through current runtime configuration:

# service ypbind status

If the service is disabled the command will return the following output:

Checking for service ypbind unused

If the service is running, this is a finding.

Fix Text (F-96377r1_fix)
The "ypbind" service can be disabled with the following command: # chkconfig ypbind off